I also experience printing from my MD802, to Autel Printer on my PC (Win7), fails/stops after about 54-59 frames (my data contains 66 items per frame; total of 81 frames in this dataset).

I originally installed Autel PC Suit V6.21 that came on the CD with the MD802.  My first online update, about 1 week ago, was Autel PC Suit V6.31 (not 6.13 ... typo above?).

I can view the full dataset of 81 frames on the MD802, but something during transmission/receipt is stopping the printing process.

It's over 12 months since you reported this problem, Unrealfighter.  I'm amazed Autel hasn't dealt with it by now?

I will be trying Eltima's RS232 DataLogger next as per your post.

  I did try using Eltima RS232 Port Logger and was able to successfully capture, and save to a TXT file, all 81 frames of data (66 items per frame) sent by the Print function of MD802 (to the COM port).

It is perhaps to be noted that the size of the TXT file, produced by copy/paste from the Autel Printer software, was 256 KB (262,565 bytes), and of a size on disk of 260 KB (266,240 bytes), for the 54 of 81 frames received.  The 256 KB number will probably flag, for someone more technically knowledgeable than I, a possible cause for the printing failure when being received by the Autel Printer software.

The size of the resultant TXT file, for all 81 frames, successfully saved by the Eltima RS232 Port Logger was 376 KB.

Conclusion:  Use the RS232 Port Logger (freeware) instead of the Autel Printer software (as released in Autel PC Suit ver 6.31) ... at least until Autel ever gets around to fixing this problem.  This problem/fix happened using Win7.

Thank you to Unrealfighter for originally posting this problem, and for identifying RS232 Port Logger as the solution.

Further testing with MD802 "printing" to Autel Printer (AP) ... regarding "print failure" and "not all frames received by AP":

- printing a DataStream with 73 frames viewable on MD ... only 58 frames received by AP at failure ... saved TXT was 281 KB.

- printing a different DataStream also with 73 frames viewable on MD ... this time only 55 frames received by AP at failure ... saved TXT was 264 KB.

- in both above cases, using Eltima RS232DL, instead of Autel Printer, enabled ALL viewable frames to be received under Win7, for saving as TXT.

Failure Hypothesis:  While the MD802 failure does seem to occur when the transmitted data goes above about 250 KB, the actual saved captures are not constant in size (ie, 281 KB, 264 KB).  As the larger DataStreams take visibly longer to complete, or fail, it is possible failure results from a TIMEOUT imposed by Autel Printer (ie, rather than buffer size allocated)?

Input Comment:  Given that Autel support staff monitor this forum, it sure would be nice if they would share what they know, or what Autel engineers can tell them!
 

 I updated my unit this morning with the latest update.  Feb-2016. 

Printing failed after 172 frames of 302. 

Thanks for the information above....

 my pmaxdiag elite printer not working any way

  Hello Autel Support:

One year later, after updating Autel PC Suit to version 6.34, the Autel Printer component STILL results in a "print failure" after receiving about 250 KB of data from the connected MD802!

My first work-around for sending large datastream captures to the PC (Win 7 32-bit) from the MD802 remains using Eltima RS232DL instead of Autel Printer.

My second work-around is removing the SD card from MD802, using a card reader to copy the DATs to the PC, and then using fware's excellent DS708Helper program to open/display/interpret the DAT in textual and graphical formats.

=> Autel Support:  Please advise how to adjust COM6 capture settings, in Win 7, for Autel Printer, so a capture limit (size? timeout?) is not encountered ... AND/OR please fix the coding in Autel Printer.  Thank you.